| Ordinal | Description | DataType
 | DataLength
 | Required | Check
 Constraints
 | Comments | 
                                
                                    | 1 | Customer
Number | string | 30 | Y |   | XREF
 lookup | 
                                
                                    | 2 | KommerceServerCustomer ID
 | integer | 4 |   |   | Used
 when new location originates in KS for a new customer also originating in KS.
 In this case the KS SQL reference can be played back to locate the proper
 business entity of type 'C'. | 
                                
                                    | 3 | Business Entity Type | string | 1 | Y | 'C' Customer | Only
 customers can have alternate locations in KS at this time. | 
                                
                                    | 4 | Address Number | string | 30 | Y |   | This
 is the integrating system's reference for this location. | 
                                
                                    | 5 | KommerceServer
 ID | integer |   |   |   | Used
 when new location originates in KS and the only thing known is the KS SQL
 reference. If the xref field is unknown KS will lookup based on the KS
 reference. | 
                                
                                    | 6 | Ship To Name | string | 50 | Y |   |   | 
                                
                                    | 7 | Address Line
 1 | string | 50 |   |   |   | 
                                
                                    | 8 | AddressLine
 2 | string | 50 |   |   |   | 
                                
                                    | 9 | Address Line
 3 | string | 50 |   |   |   | 
                                
                                    | 10 | City | string | 50 |   |   |   | 
                                
                                    | 11 | State | string | 50 |   |   | If
 the data field matches an entry in the state_province foreign key table, the
 entity_address.stat_prov_cd column is updated.
 | 
                                
                                    | 12 | Zip Code | string | 50 |   |   |   | 
                                
                                    | 13 | Country | string | 50 | Y |   | The
 Country is a free form string but for best results, send up the ISO standard
 2-character country code. KommerceServer will match this to an internal table
 so that the country can be maintained through a drop down list when adding or
 updating address locations. | 
                                
                                    | 14 | Phone | string | 25 |   |   |   | 
                                
                                    | 15 | Site ID | string | 5 |   |   | If
 the warehouse plant code does not exist in the foreign key table, a new
 warehouse will be created automatically | 
                                
                                    | 16 | Site Name | string | 30 |   |   | This
 field is only used if a new warehouse needs to be created. | 
                                
                                    | 17 | Tax Code | string | 15 |   |   | If
 this field is blank, the assumption KS makes is that this location is
 non-taxable. | 
                                
                                    | 18 | Price Sheet
 Code | string | 30 |   |   | When
 determining item prices in the storefront this is used to identify customer
 specific pricing. A Price Sheet Code can be any string but should represent
 how your ERP system organizes pricing. For example, if by country you may opt
 to send in the ISO country code. If your system has this concept it is best
 to send in a relevant value. For example, if there is a branch where pricing
 is derived then send in the branch identifier. KommerceServer does not care
 what this value is but it will use this as a first-level filter when looking
 up customer pricing. | 
                                
                                    | 19 | Price basis
Code | string | 30 |   |   | A
 secondary filter can be used for customer-specific price lookups. There can
 be more than one Price Basis per Price Sheet (e.g. LIST, WHOLESALE, MSRP,
 COST, etc.). If your ERP just has one price per Price Sheet then use a
 meaningful term like LIST or BASE for this field. This field can be left
 blank but if there are more 1 price defined for a Price Sheet it will be ambiguous so pricing cannot be determined. | 
                                
                                    | 20 | Matrix Group
Values | string | Max |   | Use
 "&" to delimit between pairs and use "=" to match a
 Group to a
 Value. If a Group has multiple values then use ","
 separator between values.
 | Refer
 to notes for the same field on the KS_CUSTOMERS export; These should be
 created consistently but KommerceServer supports this to the Entity address
 level which is also updated by the KS_CUSTOMERS export (primary) | 
                                
                                    | 21 | Default Ship Via
 |   |   |   |   | Indicates a default Ship Via code for the shipping address. During checkout in the Store is there is a freight method that is associated to this ship via code, it will be the default. | 
                                
                                    | 22 | Free Shipping Minimum
 |   |   |   |   | Indicates a minimum dollar amount required for free shipping. Only those freight methods that are eligible for customer-specific minimum will this feature be applied. Note: You must send up a  number greater then 0 for this feature to be active. |